home *** CD-ROM | disk | FTP | other *** search
- In article <woof.25.000639BE@panix.com> woof@panix.com (David A Wolfe) writes:
- >From: woof@panix.com (David A Wolfe)
- >Subject: WinIrc Problems.
- >Date: Sat, 2 Apr 1994 06:13:29
-
- >I just FTP'd a fresh copy of WinIrc and it starts to work and then
- >closes the connection. I 've never gotten past /list.
-
- >Wanddaya Thinks......?
-
- >Thanks in advance.
-
- >David
-
- i can't help you but if some one colud tell me a irc server that works with
- this winirc prog. i'ld apreciate it. the one i used to use now refuses
- conection and it dosen't work with my local server. also anyone know how to do
- actions with this program?
- thanks
-
-
- -Sargon Ftp for windows and winsock files
- arg2@po.cwru.edu 'b61503.student.cwru.edu'
- "The only perfect science is hindsight."
- From friesend@duke.usask.ca Sat Apr 2 10:49:49 1994
- Received: from duke.usask.ca by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA17111; Sat, 2 Apr 1994 17:50:01 -0500
- Received: by duke.usask.ca; id AA17756; Sat, 2 Apr 1994 16:49:49 -0600
- Date: Sat, 2 Apr 1994 16:49:49 -0600 (CST)
- From: "Darryl Friesen (4758)" <friesend@herald.usask.ca>
- Subject: RE: Problems with new MS TCP-32 and WFW 3.11
- To: Keith Moore <keithmo@microsoft.com>
- Cc: winsock@sunsite.unc.edu
- In-Reply-To: <9404020542.AA08392@netmail2.microsoft.com>
- Message-Id: <Pine.3.88.9404021650.A17457-0100000@duke.usask.ca>
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; charset=US-ASCII
-
- On Fri, 1 Apr 1994, Keith Moore wrote:
-
- > 0. The QVT/Net problem is a known bug in the MS TCP-32 sockets
- > implementation. I am currently investigating a fix.
-
- As you may or may not have heard, changing the "dispatch=sync"
- option in the QVTNET.INI file (under the [console] section) to
- "dispatch=async" seems to fix the problem of lost characters.
- I'm not sure if/how that will help you.
-
- > 1. The Mosaic problem is also a known bug that I am currently
- > investigating. You can prevent the hang by disabling the spinning
- > globe by invoking the "Options!Show Current URL/Title" menu item.
- > If the app gets into this hung state, it can usually be "kick started"
- > by minimizing then restoring the main window.
-
- Thanx for the tips.
-
- > 2. I will try to reproduce the HGopher 2.4 problem.
-
- The weird thing is that everything seems to be working fine now.
- I don't recall changing anything! Well, that's not true. I changed
- the NetHeapSize option in SYSTEM.INI (in the [386Ehn] section) from
- 20 to 64, after I received some error message suggesting I incease
- this value (I was copying rather large files from the net onto
- floppies). The only reason I used 64 was because the DNetHeapSize
- was set to that (I don't know what either do).
-
- I received mail from someone else who was having problems with the
- new TCP-32 stuff, and who also noticed his problems seemed to
- "magically" disappear after a few reboots.
-
- > Thanks for the feedback,
- > Keith Moore
- > keithmo@microsoft.com
-
- Thanx for the reply. It's nice to know there are people from
- Microsoft not only watching the net, but actively participating.
-
- - Darryl
-
- ----------------------------------------------------------------------
- Darryl Friesen, Client Services Darryl.Friesen@usask.ca
- Department of Computing Services University of Saskatchewan
- <A HREF="http://gopher.usask.ca/~friesend/">This is my Home Page</A>
- ----------------------------------------------------------------------
- "Meddle not in the affairs of dragons, for you are crunchy
- and good with ketchup." (seen in rec.arts.books.tolkien)
-
-